Skip to content

Add blog gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability#824

Draft
gardener-answering-machine wants to merge 1 commit into
masterfrom
blog/2026-01-28-gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability
Draft

Add blog gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability#824
gardener-answering-machine wants to merge 1 commit into
masterfrom
blog/2026-01-28-gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability

Conversation

@gardener-answering-machine
Copy link
Copy Markdown
Collaborator

@gardener-answering-machine gardener-answering-machine commented Jan 28, 2026

Purpose

@marc1404 This is an automatically generated draft pull request proposing a new blog post based on your Gardener review meeting presentation you gave on 2026-01-28 titled:

"Gardener Updates Its Kubernetes Version Support Policy for Better Security and Predictability"

The purpose of the blog post is to actively inform the community about new Gardener features or changes, as discussed during review meetings.

Notes to Reviewers

This draft was automatically generated by LLMs using the review meeting recording and referenced materials.
Please evaluate whether this topic is suitable for a blog post. If so, review and edit the content as needed.
If you decide the topic isn't appropriate for a blog post, feel free to close this PR and delete the branch.

⚠️ This is an experimental GenAI feature. Feedback is welcome! Please direct it to @vlerenc. Thank you!

Instructions for Reviewers

❌ If the draft isn't viable

  • Close this PR
  • Delete the branch

✏️ If the draft is viable but requires editing

  1. Clone the repository and change to the directory:
git clone https://github.com/gardener/documentation
cd documentation
  1. Check out the branch:
git fetch origin && git checkout blog/2026-01-28-gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability
  1. Review the content in website/blog/2026/01/01-28-gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability.md.
  2. Make any necessary edits, additions, or removals, and then push the changes:
git add website/blog/2026/01/01-28-gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability.md
git commit --amend --no-edit
git push origin +blog/2026-01-28-gardener-updates-its-kubernetes-version-support-policy-for-better-security-and-predictability

✅ If the draft is ready for review

  • Mark this PR as Ready for review
  • Invite additional reviewers (optional step)
  • Comment with /lgtm to approve (required step)

The documentation team will review your PR, as required by branch protection.
They will merge it once you (and any additional reviewers) have approved it.

@marc1404 Thank you for helping us share valuable updates from the Gardener project with the community!

@gardener-prow gardener-prow Bot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Jan 28, 2026
@ghost ghost added the reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) label Jan 28, 2026
@gardener-prow gardener-prow Bot added the cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. label Jan 28, 2026
n-boshnakov
n-boshnakov approved these changes Feb 2, 2026
View reviewed changes
Copy link
Copy Markdown
Contributor

@n-boshnakov n-boshnakov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@gardener-prow gardener-prow Bot added the lgtm Indicates that a PR is ready to be merged. label Feb 2, 2026
@gardener-prow
Copy link
Copy Markdown

gardener-prow Bot commented Feb 2, 2026

LGTM label has been added.

DetailsGit tree hash: b138fcc27605c68ade00bea6ae130d38eb011b00

@gardener-prow
Copy link
Copy Markdown

gardener-prow Bot commented Feb 2, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: n-boshnakov

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@gardener-prow gardener-prow Bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 2, 2026
@rfranzke
Copy link
Copy Markdown
Member

rfranzke commented Feb 18, 2026

ping @marc1404

@gardener-ci-robot
Copy link
Copy Markdown

gardener-ci-robot commented Mar 20, 2026

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 14d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as active with /lifecycle active
  • Mark this PR as fresh with /remove-lifecycle stale
  • Mark this PR as rotten with /lifecycle rotten
  • Close this PR with /close

/lifecycle stale

@gardener-prow gardener-prow Bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Mar 20, 2026
@n-boshnakov
Copy link
Copy Markdown
Contributor

n-boshnakov commented Mar 20, 2026

Hi @marc1404, could you please take a look at this PR?

@BoHristova
Copy link
Copy Markdown
Contributor

BoHristova commented Apr 15, 2026

@marc1404 Need a break from your other tasks? How about a blog post review? 😆

@gardener-ci-robot
Copy link
Copy Markdown

gardener-ci-robot commented May 15, 2026

The Gardener project currently lacks enough active contributors to adequately respond to all PRs.
This bot triages PRs according to the following rules:

  • After 30d of inactivity, lifecycle/stale is applied
  • After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
  • After 14d of inactivity since lifecycle/rotten was applied, the PR is closed

You can:

  • Mark this PR as active with /lifecycle active
  • Mark this PR as fresh with /remove-lifecycle rotten
  • Close this PR with /close

/lifecycle rotten

@gardener-prow gardener-prow Bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@n-boshnakov n-boshnakov n-boshnakov approved these changes

@marc1404 marc1404 Awaiting requested review from marc1404

Assignees

No one assigned

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. cla: yes Indicates the PR's author has signed the cla-assistant.io CLA. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. lgtm Indicates that a PR is ready to be merged. lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. reviewed/ok-to-test Has approval for testing (check PR in detail before setting this label because PR is run on CI/CD) size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@gardener-answering-machine @rfranzke @gardener-ci-robot @n-boshnakov @BoHristova